Summary

• When since is provided, behavior is unchanged: OPEN issues created_at >= since plus CLOSED issues closed_at >= since (the scoring window).
• When since is omitted, the response now contains all currently-OPEN issues with no time bound and no CLOSED history.

Lets callers asking for "current open-issue load" stop using a synthetic epoch-since workaround that fetches a full all-time payload.

Why

Mirror clients currently have to pass since=<35 days ago> for issue-discovery scoring AND a second since=<epoch> request to count current open-issue load — because OPEN issues older than the scoring window are otherwise invisible. The downstream consumer is the validator's open-issue spam multiplier (see entrius/gittensor#929 / PR #930): a miner with open issues older than 35 days currently gets a free pass on the spam gate.

Two cleaner alternatives I considered:

• Add an open_issue_count sidecar field to the response. Workable but requires both endpoint and consumer to teach a new field.
• Drop the since filter on OPEN unconditionally. Breaks the documented "issues since X" contract for scoring callers.

The since-aware behavior here keeps both contracts coherent: presence of since = scoring window, absence of since = open-issue load snapshot.

Diff

packages/das/src/api/miners/miners.service.ts

• getIssues accepts since: string | null, response shape's since is now string | null.
• SQL OPEN branch wraps the date filter in ($2::timestamptz IS NULL OR i.created_at >= $2). When $2 is null the short-circuit returns TRUE and all OPEN rows match; CLOSED branch's i.closed_at >= $2 evaluates null and yields no rows.

packages/das/src/api/miners/miners.controller.ts

• Issues route passes since ?? null through instead of calling MinersService.resolveSince(since). The PR route is untouched.
• Swagger summary/description/since docs updated to reflect both modes.

MinersService.resolveSince stays — still used by the PR route.

Test plan

• Existing scoring callers (since=<date>) get the same OPEN+CLOSED window as before — SQL plan unchanged when $2 is non-null.
• Omitting since returns all OPEN issues across all repos the mirror tracks, no CLOSED rows.
• Reviewer: spot-check the SQL planner picks the author_github_id index for the no-since case (should be the same access path; the OPEN filter degenerates to a constant).
• Reviewer: confirm no other internal callers of getIssues rely on the prior string (non-null) parameter shape.

Related

• [Bug] Mirror issue-discovery spam count ignores open issues older than lookback window gittensor#929 — validator-side bug this enables fixing.
• fix: count old open mirror issues for issue spam multiplier gittensor#930 — validator PR that will slim down once this is shipped (drop the epoch-since workaround, drop the proposed open_issue_count parsing field).